Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

v2.1.1 #147

Closed
wants to merge 1 commit into from
Closed

v2.1.1 #147

wants to merge 1 commit into from

Conversation

gurgunday
Copy link
Member

No description provided.

Signed-off-by: Gürgün Dayıoğlu <[email protected]>
@gurgunday gurgunday requested a review from Uzlopak February 28, 2024 12:49
Copy link
Member

@Eomm Eomm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we push the new version on master when we push a new release. Is there something not sync?

@gurgunday
Copy link
Member Author

@Eomm I know, and would love to do it like that, but it says main is a protected branch now

I was going to ask if this is a new thing actually - if not, could you disable that rule?

@Eomm
Copy link
Member

Eomm commented Feb 28, 2024

@gurgunday Fixed

Try again 👍🏼

@gurgunday
Copy link
Member Author

@Eomm still seeing the following:

Screenshot 2024-02-28 at 15 19 32

@Eomm
Copy link
Member

Eomm commented Feb 28, 2024

PTAL

Anyway, you are not using releasify 😭

@gurgunday
Copy link
Member Author

I swear it was on my mind to switch to it 🤣

Will use that if I can now 🙏

@gurgunday gurgunday closed this Feb 28, 2024
@gurgunday gurgunday deleted the v2.1.1 branch February 28, 2024 17:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants